Hello, and welcome to LiteStep: a Win32 Shell replacement. What is a shell, and why the reference to Win32? Well, basically a Shell is the way you interact with your computer, and the way that interface is displayed. Win32 is in reference to the OS (Operating System) platform that it functions under. Meaning, that LiteStep can run on Windows 95 (all flavors), Windows 98 (both the original and second edition), Windows NT4+, and Windows 2000 (unsupported, but has been reported to work).
Now, back to explaining what a Shell is, and what you can expect from LiteStep. For most people the interface that one is used to is created by the Microsoft Explorer Shell. That interface includes what is commonly known as the Desktop, Start Menu, and Task Bar. These things give users access to their file system and programs by plain, uncustomizable menus and icons. And, anyone that uses their computers for any amount of time, has found that this interface is cumbersome as well as boring. Hence, LiteStep comes into the arena offering an interface to your computer that is fast, stable, and ultimately highly customizable.
LiteStep, however, is not for someone who does not enjoy working with their computer, _if_ they are the one who will have to maintain the configuration. This does not mean, though, that LiteStep can not be setup for any user to give them an easy and attractive interface. Once installed and configured to a users liking, there is very little if any that one needs to do to keep LiteStep running happily. However, the configuration process can sometimes be somewhat long, and we hope to ease our new users into this, by presenting them with an initial interface that is both familiar, yet more advanced then the Explorer counterpart.
And so, what you will see when booting up your computer with LiteStep as the shell, will be a familiar, if slightly different looking, Task Bar, Start Menu, and Desktop (with shortcuts). However, there will be one completely new item to take note of. It is called the Wharf (Wharf Bar). But, to start with what we are familiar, let us first discuss the Start Menu.
Actually, it is not really called "Start Menu" in LiteStep. It is called the "Popup Menu". There are several reasons for the name change, which I think you will quickly realize once you have become more familiar with LiteStep. First off, there is no "Starting" or "Ending" place to LiteStep. You can add and/ or remove anything you like, of any part you like, that is configured by LiteStep. Now, the Popup Menu can be accessed many different ways. One way, which we are all acustomed to, is by clicking on the button in the lower left hand side of the screen. However, you will notice that, of course, the button is no longer labeled "Start" but has been renamed to "LiteStep". What, you don't like that? Well, no worries, you can easily change that button's title back to "Start" or "Any really crazy thing I feel like". Its up to you, and you can find out how to do so under the "Tips & Tricks" section. Well, there are other ways to get to your Popup Menu, and probably the most common to veteran LiteStep users, is to right-click your mouse on the Desktop. One thing you must realize about LiteStep, is that everything is completely customizable. If you don't like entries that are in the new Popup Menu, you can remove them, and even add ones that you do like.
You will find the items that you are accustomed to in the Popup Menu, like your Programs folder, just like the Explorer Shell's Start Menu contained. You will also find your Shutdown command, as well as access to your Display Properties, My Computer, Control Panel and many other standard items. What you may notice that is different is several LiteStep specific functions. These include a Popup folder that contains a list of all your currently running programs (like the Task Bar does) titled "Task Manager". You will also find a Popup folder titled "LiteStep System" which gives you access to the configuration and management of your new Shell.
Of course you will recognize and be familiar with the Task Bar, which displays your currently running programms. You can still right-click on the task representations to get the programs system menu for maximizing/minimizing programs. Your system tray will also be in its normal place in the bottom right of the screen.
Now, I know you have been wondering and thinking, enough about all the stuff that I am familiar with, lets get on to the Wharf item that was mentioned previously. Well, here we are. The Wharf is a very customizable and useful module (plugin). It has the unique ability to "host" small programs (wharf modules) that can monitor your system resources, like memory and hardrive space, to displaying a clock, to playing your favorite game "WharfAnoid" (an Arkanoid/Breakout clone). And besides these little programs, the Wharf can host folders of shortcut links to your favorite programs and utilities. The Wharf display that is first presented to you, starting at the top, is a Clock, then a folder containing entires to your LiteStep system, then a folder to common applications and utilities, then a CPU utilization monitor, and finally an item called VWM (Virtual Window Manager).
A VWM, allows a user to in essence have more then one "montior" display, or desktop. Most users, eventually, seem to get into the habit of using different VW's (Virtual Windows) to organize groups of similar applications that they have launched. But to first explain the layout and functionality of the VWM, you will notice that it is divided into four sections. Each section is a miniature representation of its corresponding VW. You can change VW's by either right-clicking on the minature window, or by "scrolling" your mouse across the edge of the current Desktop Window. It is also possible to drag an open application from one VW to another by using the VWM, and dragging the miniature windows around.
Ok, we have shown you what the interface is like, but how does it run? LiteStep itself consists of LiteStep.exe, lsAPI.dll and step.rc. Those are the core files that handle everything from configuring your display to loading different modules (plugins). Modules are different customizable programs, or interfaces to your system, such as the Popup Menu and Wharf. The Step.rc is a plain text file, that contains a set of commands that tell LiteStep what and how to perform. Inside the step.rc you can change graphics, add entries to your Popup Menu (or even remove the Popup Menu!), add in third party modules, such as replacement Task Managers. To state it plainly, you can completely change the look and content of your interface. However, all of this is done by editing a text file. You will need to have a good step.rc command reference guide handy (discussed in the Tips & Tricks section) as well as the handy "Configuring LiteStep" under the Tips & Tricks section. There are some graphical configuration programs that help ease the initial experience of managing your step.rc, but for the most part, are not powerful enough to be of use to a user that wants complete control over their interface. And of the writing of this document, the different graphical configuration programs do not support LiteStep 0.24.5 commands so we will not discuss them at this point.
So, this was supposed to be an Introduction to LiteStep? Its a novel I tell you, well, a short story anyway! :P However, the fact is, we have barely scratched the surface of what LiteStep is, let alone of what it can do. Yes, mainly what I have described here is just a rehash of the Explorer interface that you are used to, with a few fancy gadgets added along the way. The reason for this is, as you might have already been feeling some yourself, is we don't want to overwhelm our new users! And so, for those of you that tried installing our previous releases, and got overwhelmed, we hope that this release will better do the job of easing you into this wonderful and versatile Shell. With that said, what you have been presented with, is an enhanced mockup of the Explorer Shell. You will rarely see a veteran of LiteStep that has a configuration similar to this, as one will eventually modify their LiteStep interface to something that is more personal, powerful, and looks simply outstanding.
B} Why the beta?
================
LiteStep is still beta software for several reasons. One of which should have become apparent from the previous section, you have to manually hand edit a text file for the configuration of your interface. The LiteStep Development Team is constantly working on coming up with better and easier solutions to this, and a lot of that hard work will become apparent in the next major version release (b25.0).
However, LiteStep is also an ever expanding product, and as it is under continual developement with new features being added all the time, it is also only natural to consider it as beta software. Although, some would argue that in its current state, it is far more stable then the Explorer Shell, or other equivelant programs (which it is), that it should then warrent a final version 1.0 release, at least. And they would be correct, accept then, when we add new features, we would have to release beta versions to test these features out, and then finally release the next 1.2 or whatever. And so, while LiteStep is expanding so rapidly, it is easier to just keep the Beta sticker on it, so that users realize that it is under continual and active development which incorporates huge changes at times.
This should not scare off the wary though. LiteStep is a stable program, and if there are problems with it, it is generally because of an invalid setting or new third party module release that causes it. And because of this, the problem can be easily isolated and solved, with either removing or upgrading (sometimes downgrading :P) the offending part. But the beauty of LiteStep is, that in itself, it never touches another part of your system, so if it does crash, it will not directly harm other software (or hardware) on your computer, and that includes your Windows installation. If you ever want to go back to the Explorer shell, all you need to do is change your boot up command in the system.ini (win9x) or registry (winNT).
============================================
= I. Installation ==========================
============================================
After you have downloaded and run the Installation package, you will be confronted with a License Agreement. You may agree to it and continue, or exit the installation program, and delete it from your harddrive. (We'll assume you agreed) Next you will be presented with a choice to either Upgrade or perform a Full installation of the LiteStep shell. If you are performing an upgrade to your current LiteStep installation and do not want the new step.rc and graphics, then proceed to the section B} labled "Upgrade Install".
A} Full Install
===============
Once you have clicked the Full installation button, you will again be presented with another dialog, this time one that displays your system configuration and installation directory. The default Installation directory is "C:\LiteStep\" And is the recomended place to install LiteStep to. You may install anywhere you would like to however, including different drives, and paths with Long File Names and spaces. If you want to change the installation path, either manually type it in over the current path, or click the "Change" button below the box.
Once you have decided on where you want to install LiteStep to, you should be set. However, you will want to double check to make sure that our installation program has found the correct directories for your Windows folder, your Start Menu Programs folder, and that it detected the correct Operating System.
The Windows folder is needed to locate your system.ini file, as well as a few programs and system libaries. The Start Menu Programs folder is needed for creating the entry in the "Popup Menu" so that you have access to all of your installed programs, that you had access to under Windows Explorer. And the Operating System is used by the installer, so it knows what changes to make during the configuration of your system to boot with LiteStep as the shell.
If for some reason you are not comfortable with continuing the installation process, you may now choose to Exit, and no files will have been copied or system changes will have been made.
Next, choose "Install" and the LiteStep files will be copied to the installation directory you specified. NOTICE: there will be NO warning or prompt if the installer overwrites any files. Be sure to back up any previous files including your step.rc, if for some reason you are installing over your old setup. Also, note that the full install does not take notice of whether or not you currently have LiteStep loaded from the directory you are installing to, and therefor may cause errors during the installation if you are trying to overwrite a currently running installation of LiteStep. Please shutdown LiteStep, or install to a different directory to avoid these complications.
Once the files have been copied, the step.rc (the LiteStep configuration file) will be generated according to your system information. You will then be presented with a new dialog box stating that the installation has completed, and if you would like to continue to configure your system to load LiteStep as your shell. Please read what it has to say, and decide how to proceed from there. You may exit now, and you will have to manually configure your system (more on that under Tips & Tricks), or choose to continue and let the installer do it for you.
If you are running Windows 95, Windows 98, or Windows 98se continue with the following section - a) Windows9x, otherwise if you are running Windows NT4+ or Windows 2000 (unsupported), proceed to the section - b) Windows NT.
a) Windows9x
============
If you chose to continue, you will be presented with a dialog box that shows you your system.ini file configuration, which controls what shell is to be loaded when your system starts. If you do not understand what is going on here, but you do want LiteStep loaded as your Shell, just do a double check to make sure the new information points to the directory where you had LiteStep installed to, then click "Apply". That is it, you are done, and on your way to a better way to access and interact with your computer! You can choose to reboot now, or later, but when you do, you will never look back.
For those of you who want to use a Shell manager, or are already running a Shell manager, you can modify the setting if you like, or hit the Cancel button, and then modify your Shell Manager settings to point to your new installation of LiteStep. (Refer to your relevant Shell manager's documentation).
EXTRA INFO: If you chose to apply the settings to your system.ini file, the old setting was commented out and placed under ";oldshell=" in the "[boot]" section. So it would most likely look like: ;oldshell=explorer.exe
b) WindowsNT
============
If you chose to continue, you will be presented with a dialog box that asks whether you have administrative access to your computer with the current user login. Read what it has to say, and choose accordingly. Next you will be shown a configuration dialog box for setting up your registry settings. It is suggested that you leave the value for the second option "BrowseNewProcess", to "YES". Otherwise you may encounter problems while running explorer.exe as a File manager under LiteStep. If you do not understand what is going on here, but you do want LiteStep loaded as your Shell, just do a double check to make sure the new information points to the directory where you had LiteStep installed to, then click "Apply". (If you chose "Admin" from the previous dialog you will be presented with two dialog boxes, and will need to click "Next" on the first one, then "Apply" on the second one. The first Dialog is for setting the shell to LiteStep globally, and the second Dialog is for setting it to the current user. No changes will be made until you click "Apply")
B} Upgrade Install
==================
Before you continue with the Upgrade Installation, it is a good idea to shut down your current instance of LiteStep. You can do this by issuing the "!Quit" command, however, if you do so, be sure to have a running instance of the Explorer File manager open, so you can restart the new version of LiteStep when your finished installing. Although, the installer will run your newly upgraded LiteStep shell automatically for you if you tell it to, but it is a good precaution none the less.
If you keep LiteStep running during the upgrade procedure, you will be confronted with a dialog box, asking you to shut down LiteStep. You may ignore this if you are extracting the files to a different directory from where you are currently running LiteStep. However, do NOT try to overwrite your old files if they are currently in use! The installation will fail, and you will not have upgraded to the latest release.
After you have proceeded from there, you will be asked to confirm your installation directory, along with being given the option to install the different components in seperate folders, or all in the same folder. If you have any doubt, just direct all three options to your main LiteStep folder. If you have organized your modules differently or to more folders then you are given the option to install to, we suggest that you extract all of these files to a temporary directory, and manually copy them over to your own custom locations. The following describes what each directory means for installing the files:
LiteStep Directory <- This is where "litestep.exe" and "lsapi.dll" are placed.
Load Module Directory <- This is where "desktop.dll", "hook.dll", "hotkey.dll", "popup.dll", "shortcut.dll", "sysvwm.dll", and "wharf.dll" are placed.
Wharf Module Directory <- This is where "lsvwm.dll", "lstime.dll", "lsclock.dll", and "lscpu.dll" are placed.
Once you have installed the files, you will be prompted whether or not to run your newly upgraded installation of LiteStep. However, if there is a current instance of LiteStep running you will be told so, and the newly updated files will not be run, but everything was successfully installed. You are then finished installing the upgrade. Enjoy.
============================================
= III. Tips & Tricks========================
============================================
A} Installation stuff
=====================
The following explains how to manually configure your system to run LiteStep as the shell without the use of this installer. As well as explaining how to restore your system to using Explorer.exe as the shell from both within Windows, or from a DOS prompt if you system did not boot.
a) Windows 9x
=============
Open up the file called "system.ini" with any text editor (notepad.exe is suggested). This file is located in your Windows directory which is generally in "c:\windows\". You will need to locate the line in "system.ini" that begins with "shell=". This can be found in the "[boot]" section which is usually located at near the top of the "system.ini" file. Most likely the full line will look like "shell=EXPLOER.EXE". However, if you can not locate the "shell=" line under the "[boot]" section of you "system.ini" file you may safely create the line yourself, making sure that it is underneath of the "[boot]" section. Now, remove the "EXPLORER.EXE" part of the line and replace it with "c:\litestep\litestep.exe", of course adjusting that to the location of "litestep.exe" on your computer. So for example, you may have something that looks like this:
(from c:\windows\system.ini)
[boot]
shell=EXPLORER.EXE
and you would change it to look like this:
[boot]
shell=c:\litestep\litestep.exe
Then, make sure you save the file. Exit your text editor and reboot your system. You will now have LiteStep running as your shell as long as nothing went wrong.
If something DID go wrong, do not worry. It is NOT a big deal. Even if Windows yells at you and says you need to re-install Windows, please please do not! It is not necessary! Ok, now just reboot your computer, and right when the bios finishes loading, and it changes to the screen that says "Starting Windows 98" (or 95) press your F8 key like you mean it. A menu will appear. Choose the option "Boot in Safe Dos Mode". Once finished you will see a normal DOS command prompt looking something like: "C:\>". Type the following without the quotation marks: "edit c:\windows\system.ini". And press the "Enter" (Return) key. Of course adjusting the command to wherever your system.ini file is located on your system. Again, find the line that says "shell=" under the "[boot]" section. Check to see if perhaps you mispelled something which caused the error. If nothing was wrong, then simply change the command back to point to "EXPLORER.EXE". So now it should look something like the following:
[boot]
shell=EXPLORER.EXE
To exit the editor, press the "Alt" button, then the "F" button. Use your arrow keys to move down to the "Exit" option, and when prompted to save the file, choose "Yes". You can now either hit your reset button on your computer or press the "Ctrl" key and the "Alt" key and the "Del" (delete) key all at the same time, and your computer will be restarted. You should then be fine with your Explorer interface back. Feel free to contact us at qa@litestep.org for assistance in getting your system running with LiteStep.
b) Windows NT
=============
Using Regedit32.exe open up your registry, and make the following changes according to the different choices that you have (Be sure to make a backup of the registry, and write down the current values of each setting before changing them, so that you have a reference to what they were if you ever want to restore the old settings):
LitesStep NT Reg settings.
==========================
For One user with admin access, and always wants LiteStep as the shell:
If you do not have administrative access, use the first set of registry commands, but do not set any of the HKEY_LOCAL_MACHINE entries. NOTE: you will NOT be able to use explorer.exe as a FileManager without it taking over the system and disabling LiteStep. This includes accessing any Explorer related items. Try instead to use Internet Explorer or alternate file managre to access your file system. You have been warned! (this is only if you do not set the HKEY_LOCAL_MACHINE entries)
===========================
I suggest backing up your registry files, before doing the above changes, to a boot floppy, so you can restore them if necessary. Alternatively, there is a rumour that once NT loads and the Shell does not come up you can press the "Ctrl" and "Alt" and "Del" buttons at the same time, and a Task Manager will pop up. From there you can run "explorer.exe" and then load your registry as you did above with "regedit32.exe" and restore the settings to what they were before you changed them to use LiteStep. Then reboot, and you are good to go. Hopefully.
B} Configuring LiteStep
=======================
First you will need a good step.rc command reference guide. There is one in your "docs\" directory, or one is available online at http:\\www.gangsterpump.com\litestep\. These are something that you should keep around you at all times if you are planning on doing any changes to the step.rc file. If you feel the need, print them out and study them.
If you want to create graphics you should go download a good image editor like Paint Shop Pro (www.jasc.com). However, you can just Paint that comes bundled with your Microsoft Windows Operating System. If it is not installed, refer to your Windows documentation.
If you plan on creating modules (plugins) for LiteStep you will probably need Microsoft Visual C++. However, the LiteStep source code can be compiled with other free programs. There are also plugin SDK's for Delphi that are available, currently you can find these at http://floach.pimpin.net/mindstorm/
If you just want to modify your step.rc to re-arrange your layout and load different modules, then load up that step.rc reference guide and lets get to this! However, first there are two main things you need to remember while editing your step.rc (LiteStep configuration file). First is you need to save the "step.rc" file when you change an item. Secondly, you need to issue the LiteStep "Recycle" command for any changes to take affect. You can do that with the default setup by pressing the "Recycle" bar on the bottom of the Wharf, or pressing the key combination "Win C". Both of those ways of "recycling" actually just issue the action (bang) command "!Recycle" to LiteStep. All action (bang) commands start with an exclamation mark.
For a quick initiation. Your step.rc commands are organized into "sections" each section has a beggining and ending header. For example the configuration of your Popup menu which is controlled by the popup.dll has two sections. One for configuring the way it looks and functions, and another for inserting/removing items from the popup menu. All lines beggining with an astricks (*) are entry commands to adding items. *Popup adds an item to the popup, *Wharf adds an item to the Wharf, etc. You will get the hang of it as we go along.
To start out, open up your step.rc and scroll to the section that has "(Begin) Desktop.dll Settings [TaskBar]" in the section header. This part is what is controlled by the module "desktop.dll" and that includes the TaskBar. As mentioned previously in this readme, you can change the Caption of the "Start" button in the TaskBar. This is how you do it:
Find the line that says: StartButtonText "LiteStep"
Replace "LiteStep" with what ever text string that you would want. So, perhaps you changed it to this: StartButtonText "There ain't no Start!"
Now, issue the "Recycle" command (as explained above). You will notice that the text string you entered may have been cut off. If so find the line that reads: StartButtonSize "50"
Change it to a larger (or smaller size) and save the step.rc and Recycle. Do this until you find the correct length. There is of course more you can change about that button, but we will leave it to you to discover by using the step.rc command references.
Here is an extremely useful Popup Menu trick. Find the section that reads "(Begin) Popup.dll Entries" and find the line: *Popup "Programs" "!PopupDynamicFolder:$StartMenuDir$"
That line is what creates the Popup entry that gives you access to your programs in your Start Menu. However, it can get to be extremely large and obnoxious to use. Try customizing your menu by doing the following.
Go to your LiteStep directory. If the folder "Shortcuts" does not exist in it create one. You should now have a Folder that looks somewhat like this: "c:\litestep\shortcuts\". Now inside of the Shortcut folder, create several more folders of your choice that will be relevant to the different types of applications on your computer. For instance, the following is a good general folder layout:
c:\litestep\shortcuts\Games\
c:\litestep\shortcuts\General\
c:\litestep\shortcuts\Imaging\
c:\litestep\shortcuts\Internet\
c:\litestep\shortcuts\Media\
c:\litestep\shortcuts\Misc\
c:\litestep\shortcuts\Utilities\
c:\litestep\shortcuts\WPTools\
Once you have created those folders, go through your existing Start Menu, and start copying over only the links to the programs themselves (Don't worry about copying over links to help files and the like) Put your Soliatre, Quake, MineSweeper, Half-Life etc links into the Games folder. Put all your graphic editing links like PhotoShop, PSP, Paint etc links into the Imaging folder. Continue to arrange all of your programs into the respecitive folders. This may take you a few minutes, but you should find it useful in the end.
Now, put a semicolon (;) in front of the line that I showed you above: *Popup "Programs" "!PopupDynamicFolder:$StartMenuDir$"
That will remove the Start Menu from your Popup, without you actually deleting the line. Now place the following new lines in its place:
Save your step.rc and issue the Recycle command. You will now have a much easier to access and nicer popup menu. No more going through 5 different levels of popups to get to the program that you want. The only drawback is of course that if you install a new program, you will need to copy the new link over to the appropriate folder and recycle. An alternative (yet slower) command to use instead of "!PopupFolder:" in the above items is "!PopupDynamicFolder:" What this does, is if you add a new link to any of those folders, you do not need to recycle for the Popup menu to recognize the folder contents have been updated. If you plan on doing a lot of adding and removing items from the Popup folders, then this would be a good idea to use, however if not, I do not suggest using it, as it is just a slight bit slower.
Next lets take a look at the section with the header "(Begin) Wharf.dll Entries". Here we will be able to change the contents of the Wharf bar. It is quite similar to the layout of the *Popup configuration commands. The tip to share here, is the combining of multiple bitmaps into one. Take a look at the line that reads:
As you can see there are two bitmaps specified seperated by a pipe (|), "wsteprc.bmp" and "wsteprc2.bmp". These images are (must be) of the same dimensions, and in this case are both 64x64 pixels, using Pink for transparency 255,0,255 RGB. All LiteStep images use that color for transparency. The usefulness in this is, you can create "peices" of images that are common throughout all of your bitmaps. In this case "wsteprc.bmp" is a bitmap of an icon, and "wsteprc2.bmp" is a bitmap of text. In this way, one could reuse that same bitmap in another place without having to create a new item that does not contain the text specific to the item you are using it for. The order of appearance (or layers) is the first one specified is on top, and the last one is on the bottom, with all others falling in between accordingly. Yes you can specify more then one bitmap, just make sure to seperate them with the pipe character (|). The big benefit of this, besides saving you extra time in reproducing the same graphic for every item, is the amount of drive space you save. This is especially important when creating Themes for distrobution.
Ok, one last one. Are you tired of searching through your step.rc to change the location of programs everytime you change computers, or move programs around? Well, your solution is to use $E-Vars$ (Enviromental Variables). This is explained fairly well in the Official documentation, however, here is a quick run down/ideas for there use. In your step.rc locate the line that says: StartMenuDir "c:\windows\start menu\programs\"
That is a user defined $E-Var$, to access it, you can simply use "$StartMenuDir$" anywhere in your step.rc inplace of where you would normally insert the text "c:\windows\start menu\programs\". The following are a few ideas, put them in your step.rc in the relevant places and see what happens.
Browser "c:\program files\opera\opera.exe"
FtpClient "c:\program files\cuteftp\cutftp32.exe"
EmailClient "c:\program files\eudora\eudora.exe"
And now any time you change the location of a program, just change those simple lines to point to the correct place, and then anywhere you use $E-Vars$ in your step.rc, it will automatically use the new location of the program. For example you could use the following in your Popup Entries:
*Popup "Internet" Folder
*Popup "Browser" "$Browser$"
*Popup "FTP Client" "$FtpClient$"
*Popup "Email Client" "$EmailClient$"
*Popup ~Folder
Save your step.rc and recycle. You now have a new Internet folder that contains items to your internet applications. You can use "$E-Vars$" for anything string of text as well. You aren't limited to what they can contain.
Hopefully the above tips will get you on your way to configuring your step.rc and LiteStep system to work, look, and run how you want it to. Keep your step.rc command reference handy and you should be in good shape. Keep LiteSteppin'!
============================================
= III. Help & Info =========================
============================================
A} On-Line help & docs
======================
http://www.litestep.org/help/ <- a general introduction to LiteStep along with different resources to various help items.
http://www.litestep.org/help/ls-024_5/ <- the official LiteStep 0.24.5 documentation.
http://www.litestep.org/files/readmes/ls-024_5.txt <- this readme file.
http://www.litestep.com/DocsProject/245/manual.html <- the official LiteStep 0.24.5 documentation.
